Methods and systems for building a view of a dataset incrementally according to data types of user-selected data fields

ABSTRACT

A process builds a view of a dataset. The process displays a graphical user interface window, including: a schema display region; a visualization region; and a shelf region that includes multiple shelves. The process detects user input to place a data field icon from the schema display region into the visualization region. Upon ceasing to detect the user input, the process associates the data field icon with a first shelf according to its data type and data types corresponding to other data field icons, if any, previously associated with the shelves, and then places the first data field icon within the first shelf. The method further includes determining a view type based on the data field icon and the association of the data field icon with the first shelf, and generating a graphical representation in the visualization region in accordance with the determined view type.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 15/436,706, filed Feb. 17, 2017, entitled “Computer Systems and Methods for Ranking Data Visualizations using Different Data Fields,” which is a continuation of U.S. patent application Ser. No. 14/549,482, filed Nov. 20, 2014, entitled “Computer Systems and Methods for Automatically Viewing Multidimensional Databases,” which is a continuation of U.S. patent application Ser. No. 13/352,137, filed Jan. 17, 2012, entitled “Computer Systems and Methods for Automatically Viewing Multidimensional Databases,” now U.S. Pat. No. 9,600,528, which is a continuation of U.S. patent application Ser. No. 11/223,658, filed Sep. 9, 2005, entitled “Computer Systems and Methods for Automatically Viewing Multidimensional Databases,” now U.S. Pat. No. 8,099,674, each of which is hereby incorporated by reference in its entirety.

FIELD OF THE INVENTION

This invention relates generally to computer systems and methods for displaying data such as database information. The invention relates specifically to a computer system and method for displaying data clearly and effectively based upon the types of data found in a dataset.

BACKGROUND OF THE INVENTION

Data is more than the numbers, values, or predicates of which it is comprised. Data resides in multi-dimensional spaces which harbor rich and variegated landscapes that are not only strange and convoluted, but are not readily comprehendible by the human brain. The most complicated data arises from measurements or calculations that depend on many apparently independent variables. Data sets with hundreds of variables arise today in many contexts, including, for example: gene expression data for uncovering the link between the genome and the various proteins for which it codes; demographic and consumer profiling data for capturing underlying sociological and economic trends; sales and marketing data for huge numbers of products in vast and ever-changing marketplaces; and environmental measurements for understanding phenomena such as pollution, meteorological changes and resource impact issues. International research projects such as the Human Genome Project and the Sloan Digital Sky Survey are also forming massive scientific databases. Furthermore, corporations are creating large data warehouses of historical data on key aspects of their operations. Corporations are also using desktop applications to create many small databases for examining specific aspects of their business.

One challenge with any of these databases is the extraction of meaning from the data they contain: to discover structure, find patterns, and derive causal relationships. Often, the sheer size of these data sets complicates this task and means that interactive calculations that require visiting each record are not plausible. It may also be infeasible for an analyst to reason about or view the entire data set at its finest level of detail. Even when the data sets are small, however, their complexity often makes it difficult to glean meaning without aggregating the data or creating simplifying summaries.

Among the principal operations that may be carried out on data, such as regression, clustering, summarization, dependency modeling, and classification, the ability to see patterns rapidly is of paramount importance. Data comes in many forms, and the most appropriate way to display data in one form may not be the best for another. In the past, where it has been recognized that many methods of display are possible, it has been a painstaking exercise to select the most appropriate one. However, identifying the most telling methods of display can be intimately connected to identifying the underlying structure of the data itself.

Business intelligence is one rapidly growing area that benefits considerably from tools for interactive visualization of multi-dimensional databases. A number of approaches to visualizing such information are known in the art. However, although software programs that implement such approaches are useful, they are often unsatisfactory. Such programs have interfaces that require the user to select the most appropriate way to display the information.

Visualization is a powerful tool for exploring large data, both by itself and coupled with data mining algorithms. However, the task of effectively visualizing large databases imposes significant demands on the human-computer interface to the visualization system. The exploratory process is one of hypothesis, experiment, and discovery. The path of exploration is unpredictable, and analysts need to be able to easily change both the data being displayed and its visual representation. Furthermore, the analyst should be able to first reason about the data at a high level of abstraction, and then rapidly drill down to explore data of interest at a greater level of detail. Thus, a good interface both exposes the underlying hierarchical structure of the data and supports rapid refinement of the visualization.

Tableau® software and Microsoft® Excel® are examples of visualization software that create views of datasets. Tableau® Table Drop allows users to drag data fields onto a Tableau® view to create a graphical views. When the view is a text table, the behavior is similar to the drags supported by Excel® Pivot Tables. For example, dragging a quantitative data type (Q) onto a text table (X=O Y=O T=Q, where “O” stands for ordinal data), extends the table to put the two measures next to each other (X=O Y=O,Om T=Qm, where “Om” stands for measure ordinal data and “Qm” stands for measure quantitative data). However, Tableau® Table Drop has functionality not found in Excel® Pivot Tables in that it may change the view type of a view when fields are dragged onto the view. For example, dragging a Q onto a bar chart (X=O Y=Q) can create a stacked bar chart (X=O Y=Qm C=Om). Or, if there was already a field with a color encoding (X=O Y=Q C=F) in the view, then the software can transform the Q data into Qm data, and place the measure names on the Level of Detail encoding (X=O Y=Qm C=F L=Om). With scatter plots, the logic is similar, except the transformation of Q to Qm and placement of measure names on the Level of Detail encoding are triggered when an existing field already has a shape encoding.

In addition to various software programs, the known art further provides formal graphical presentations. Bertin's Semiology of Graphics, University of Wisconsin Press, Madison Wisconsin, (1983), is an early attempt at formalizing graphic techniques. Bertin developed a vocabulary for describing data and techniques for encoding the data into a graphic. Bertin identified retinal variables (position, color, size, etc.) in which data can be encoded. Cleveland (The Elements of Graphing Data, Wadsworth Advanced Books and Software, (1985), Pacific Grove, Calif.; and Visualizing Data, (1993), Hobart Press) used theoretical and experimental results to determine how well people can use these different retinal properties to compare quantitative variations.

Mackinlay's APT system (ACM Trans. Graphics, 5, 110--141, (1986)) was one of the first applications of formal graphical specifications to computer generated displays. APT uses a graphical language and a hierarchy of composition rules that are searched through in order to generate two-dimensional displays of relational data. The Sage system (Roth, et al., (1994), Proc. SIGCHI ′94, 112-117) extends the concepts of APT, providing a richer set of data characterizations and forming a wider range of displays. The existing art also provides for the assignment of a mark based upon the innermost data column and row of a dataset (Hanrahan, et al., U.S. patent application Ser. No. 11/005,652, “Computer System and Methods for Visualizing Data with Generation of Marks”). Heuristically guided searches have also been used to generate visualizations of data (Agrawala, et al., U.S. Pat. No. 6,424,933, “System and Method for Non-Uniform Scaled Mapping”).

A drawback with the formal graphical specifications of the art is that they do not provide any guidance to a user as to useful and clear visual formats in which a set of data could be rendered. The rendering of the data is such that there is no analysis to examine the resulting visualization for clarity or usefulness. Further, in the use of heuristic searches (trial-and-error method), the searches fail, leaving the user with the problem of finding clear or useful views. Heuristic algorithms can have complex behavior that creates a poor user experience. When a user does not understand why a heuristic algorithm generates certain views, the algorithm becomes unpredictable to the user and the user will not be inclined to use the algorithm.

Based on the background state of the art, as described herein, what is needed are improved methods and graphical interfaces wherein the initial visualization of data has been determined to be a clear and useful visualization, and this visualization is then automatically presented to the user.

SUMMARY OF THE INVENTION

The present invention provides improved methods for visualizing data.

A first aspect of the invention provides a computer implemented method for automatically and visually displaying a graphical representation of a dataset, comprising: receiving a user selected and ordered plurality of fields; selecting a resulting view for displaying the dataset based on the order of the user selected fields; and displaying the dataset or a transformation of the dataset according to the resulting view. In one embodiment, the dataset is retrieved from a remote database. In another embodiment, rules are used to select the resulting view. In yet another embodiment, the rules are predetermined. In other embodiments, the rules are determined by the user's preferences or usage. In a further embodiment, heuristics are used to select the resulting view.

A second aspect of the invention provides a computer implemented method for automatically and visually displaying a graphical representation of a dataset with a plurality of tuples, comprising: forming a plurality of rated alternative views, each alternative view showing all tuples, or a transformation of all tuples, in the dataset; selecting a resulting view from the plurality of alternative views, based upon a user selected option; and displaying the dataset according to the resulting view. In one embodiment, the dataset is retrieved from a remote database. In another embodiment, rules are used to select the resulting view. In yet another embodiment, the rules are predetermined. In other embodiments, the rules are determined by the user's preferences or usage. In a further embodiment, heuristics are used to select the resulting view. In yet a further embodiment, when the user selected option is a first option, the selecting step further comprises: ranking the plurality of alternative views according to a rating system; and assigning the resulting view as the highest ranked alternative view. In still another embodiment, when the user selected option is a second option, the selecting step further comprises: displaying a list of the alternative views; receiving the user's selection of an alternative view; and assigning the resulting view as the alternative view selected by the user.

A third aspect of the invention provides a computer program product for use in conjunction with a computer system, the computer program product comprising a computer readable storage medium and a computer program mechanism embedded therein, the computer program mechanism for automatically and visually displaying a graphical representation of a dataset, the computer program mechanism comprising: a field receiver for receiving a user selected and ordered plurality of fields; a resulting view selector for selecting a resulting view for displaying the dataset based on the order of the user selected fields; and a dataset displayer for displaying the dataset or a transformation of the dataset according to the resulting view. In one embodiment, the dataset is retrieved from a remote database. In another embodiment, rules are used to select the resulting view. In yet another embodiment, the rules are predetermined. In other embodiments, the rules are determined by the user's preferences or usage. In a further embodiment, heuristics are used to select the resulting view.

A fourth aspect of the invention provides a computer program product for use in conjunction with a computer system, the computer program product comprising a computer readable storage medium and a computer program mechanism embedded therein, the computer program mechanism for automatically and visually displaying a graphical representation of a dataset with a plurality of tuples, the computer program mechanism comprising: an alternative view former for forming a plurality of rated alternative views, each alternative view showing all tuples, or a transformation of all tuples, in the dataset; a resulting view selector for selecting a resulting view from the plurality of alternative views, based upon a user selected option; and a dataset displayer for displaying the dataset according to the resulting view. In one embodiment, the dataset is retrieved from a remote database. In another embodiment, rules are used to select the resulting view. In yet another embodiment, the rules are predetermined. In other embodiments, the rules are determined by the user's preferences or usage. In a further embodiment, heuristics are used to select the resulting view. In yet a further embodiment, when the user selected option is a first option, the resulting view selector further comprises: an alternative view ranker for ranking the plurality of alternative views according to a rating system; and a view assignor for assigning the resulting view as the highest ranked alternative view. In still another embodiment, when the user selected option is a second option, the resulting view selector further comprises: a list displayer for displaying a list of the alternative views; a selection receiver for receiving the user's selection of an alternative view; and a view assignor for assigning the resulting view as the alternative view selected by the user.

A fifth aspect of the invention provides a computer system for automatically and visually displaying a graphical representation of a dataset, the computer system comprising: a central processing unit; a memory, coupled to the central processing unit, the memory storing: the dataset; a programming module comprising, comprising: instructions for receiving a user selected and ordered plurality of fields; instructions for selecting a resulting view for displaying the dataset based on the order of the user selected fields; and instructions for displaying the dataset or a transformation of the dataset according to the resulting view. In one embodiment, the dataset is retrieved from a remote database. In another embodiment, rules are used to select the resulting view. In yet another embodiment, the rules are predetermined. In other embodiments, the rules are determined by the user's preferences or usage. In a further embodiment, heuristics are used to select the resulting view.

A sixth aspect of the invention provides a computer system for automatically and visually displaying a graphical representation of a dataset with a plurality of tuples, the computer system comprising: a central processing unit; a memory, coupled to the central processing unit, the memory storing: the dataset; a programming module comprising: instructions for forming a plurality of rated alternative views, each alternative view showing all tuples, or a transformation of all tuples, in the dataset; instructions for selecting a resulting view from the plurality of alternative views, based upon a user selected option; and instructions for displaying the dataset according to the resulting view. In one embodiment, the dataset is retrieved from a remote database. In another embodiment, rules are used to select the resulting view. In yet another embodiment, the rules are predetermined. In other embodiments, the rules are determined by the user's preferences or usage. In a further embodiment, heuristics are used to select the resulting view. In yet a further embodiment, when the user selected option is a first option, the instructions for selecting further comprises: instructions for ranking the plurality of alternative views according to a rating system; and instructions for assigning the resulting view as the highest ranked alternative view. In still another embodiment, when the user selected option is a second option, the instructions for selecting further comprises: instructions for displaying a list of the alternative views; instructions for receiving the user's selection of an alternative view; and instructions for assigning the resulting view as the alternative view selected by the user.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an illustration of a computer system that facilitates the visualization of a dataset in a clear and useful form.

FIG. 2 is a flowchart of the steps through which a system proceeds in one embodiment of the present invention.

FIGS. 3a and 3b are illustrations of one way of presenting an embodiment of the present invention to a user.

FIGS. 4a-4i are rules whereby a field may be added to an existing view or whereby a field may be used as the only field in a view.

FIGS. 5a-5c are examples of different views of a single dataset.

FIGS. 6a and 6b are flowcharts of the steps through which a system proceeds in another embodiment of the present invention.

FIG. 7 is a table showing the criteria for forming views of a dataset and a rating system for one embodiment of the present invention.

FIGS. 8a-8l are resulting views, based upon an embodiment of the present invention.

Like reference numerals refer to corresponding parts throughout the several views of the drawings.

DETAILED DESCRIPTION OF THE INVENTION

The present invention provides methods, computer program products, and computer systems for automatically providing a user with a clear and useful view of a dataset. In a typical embodiment, the present invention builds and displays a view of a dataset as a user adds fields to the dataset or as a dataset is accessed, such that the view is clear and useful, and is automatically presented to the user. An advantage of the present invention is that data is presented in a clear and useful form automatically.

The present invention operates on a set of data, called a dataset, that are made up of tuples. As one skilled in the art will realize, the dataset can be a relational database, a multidimensional database, a semantic abstraction of a relational database, or an aggregated or unaggregated subset of a relational database, multidimensional database, or semantic abstraction. Fields are categorizations of data in a dataset. A tuple is an item of data (such as a record) from a dataset, specified by attributes from fields in the dataset. A search query across the dataset will return one or more tuples. Fields contain data that are of particular types, and each field is of a particular type. These types include:

Data Type Symbol Ordinal O Ordinal time (date) Ot Dependent ordinal Od (categorical measure) Measure names Om Quantitative Q Independent Quantitative Qi (dimension) Dependent Quantitative Qd (measure) Measure values Qm Quantitative time Qt Quantitative position Qx Measure names may include an ordinal field whose domain is the name of one or more Qd fields. Measure values may include a dependent quantitative field whose domain and values are the blending of the Qd fields whose names appear in the domain of measure names.

A view is a visual representation of a dataset or a transformation of that dataset. Text table, bar chart, and scatter plots are all examples of types of views. Views contain marks that represent one or more tuples in a dataset. In other words, marks are visual representations of tuples in a view. A mark is typically associated with a type of graphical display. Some examples of views and their associated marks are as follows:

View Type Associated Mark Table Text Scatter Plot Shape Bar Chart Bar Gantt Plot Bar Line Graph Line Segment Circle Graph Circle

FIG. 1 is an illustration of a computer system that facilitates the visualization of a dataset in a clear and useful form. System 100 includes memory 102, CPU 180, user interface 184, storage unit 194, disk controller 192, and bus 182 that connects all of system 100's elements together. System 100 may also have network connection 196 for communication with other systems on a network. System 100 also includes memory 102, which stores operating system 104, file system 106, as well as various other modules related to the present invention. Additionally, memory 102 may also store dataset 140, which contains tuples. System 100 may also be connected to database 150 where a dataset may be retrieved and stored in memory 102. Memory 102 also stores computer program mechanisms that are necessary to some embodiments of the present invention.

In FIG. 2, flowchart 200 describes the steps through which a system proceeds in one embodiment of the invention. At step 202, ordered fields selected by a user are received. A resulting view is selected at step 204, and the dataset is displayed at step 206 according to the resulting view.

The computer system modules used to perform this embodiment of the invention are shown in FIG. 1. Field receiver 108 performs step 202 by receiving ordered fields selected by the user. Resulting view selector 110 performs step 204 and selects a resulting view. Dataset displayer 112 performs step 206 and displays the dataset according to the resulting view.

According to one embodiment of the invention, resulting view selector 110 selects the resulting view by choosing rule(s) for adding the user selected ordered fields (step 208). This is accomplished by rule chooser 114. Rule applier 116 then applies the rule(s) to determine the resulting view's view type (step 210). In another embodiment of the invention, before rule chooser 114 chooses rule(s), view determiner 118 determines whether a first view exists (step 212). In yet another embodiment of the invention, the dataset is displayed in step 206 when mark chooser 126 chooses a mark for the resulting view (step 218), and dataset renderer 128 renders the dataset according to the mark (step 220).

FIGS. 4a-4i show sets of rules that are associated with adding (or “dropping”) fields with particular data types. The field may be the only field in a view, or the field may be in addition to fields already in an existing view. When dropping a field, the field is added either as a column or a row, or it may be encoded. Encodings include color, size, and shape to represent a value. For example, red may represent all values between 1 and 10. The following convention is used for operators in the rules shown in FIGS. 4a-4i (“E” designates encoding):

Operator Limitations =   Assign field to a clause Left hand side is a +=  Add field to the end of the clause column or row (some rearrangements may occur) Right hand side must be O or Qd *=  Blend field with column or row Right hand side (blend Qd with first E accepting/containing a must be Qd Qd). The blend will result in Qm being on column or row, and an Om being added to the view. ?   Guard the action. Only add if the Unary column or row accepts the field and the cardinality of the field is less than the cardinality associated with the column or row.

The sets of rules are organized first by the type of the field that is dropped (e.g. O or Qd), and then by the type of the view that the field is being dropped onto. The rules are further broken down by the type of the view. The type of a view depends on their innermost row and column. For example, OO is a view with ordinal fields in the row and column; OQ is a view with an ordinal field in the row and a quantitative field in the column; and φ is an empty view with no fields. For each type of field being dropped, a rule table is shown containing the rules for each type of view into which the field is being dropped. The columns of the rule tables represent the contents of the innermost field on the column (X), and the rows of the rules table the innermost field on the row (Y).

In step 208, rule(s) for adding the user selected field's data type are chosen. For example, if a user selected field is an ordinal, then the set of rules in FIG. 4a would be used. Or, if a user selected field is an independent quantitative, then the set of rules in FIG. 4d would be used. If in step 212 view determiner 118 determines that no first view exists, then rule chooser 114 would choose the rule in row 1 column 1 of FIG. 4a as the rule in step 208. If in step 212 view determiner 118 determines that a first view exists, and the first view contains an independent quantitative field in the innermost column and an independent quantitative field in the innermost row of the first view, then rule chooser 114 would select the rule in row 3 column 3 of FIG. 4a as the rule in step 208. Finally, in step 210, rule applier 116 applies the rule selected by rule chooser 114. If no first view exists, then the resulting view will contain a single column (Y=O). If the first view was of the QiQi type, then the resulting view will contain an encoded field (E+=O).

Notes for FIG. 4 a:

-   -   E+=O adds to shape then color then Z. The O is always added.     -   ?E+=O conditionally adds to shape then color. O is only added if         the encoding is empty. And if the cardinality of the field is         less than the cardinality supported by the encoding.     -   In the above rules, the shape shelf is only considered if the         mark is shape.     -   Nothing is dropped on an encoding if the mark is a bar. That is,         the guarded rule always fails. We try to avoid stacking of bars         (more generally, nothing is dropped if we are stacking because         we don't know if the field supports stacking (is additive)).     -   The Qi row represents Qi on the Y axix. These cases are rare         because Qi is normally placed on the X axis.     -   Notes for FIG. 4 b:     -   The guard E=φ? checks whether the encoding (text or size) is         empty.     -   E*=Qd first tries to add to text then size then color then Z.     -   ?E*=Qd first tries to add to text then size.     -   In the above rules, the text shelf is only considered if the         mark is text.     -   An encoding accepts the Qd if it is empty or already contains a         Qd. It does not accept the Qd if it contains an O.     -   If the field accepting the encoding contains a Qd or a Qm, then         the new Qd is blended with the contents to produce a Qm. If an         Om is generated by the blend, it is added to the column shelf if         that shelf is empty, otherwise it is added to the row shelf.     -   The Ot rules take precedence over the O rules.     -   The guard Y=Ot? checks whether the Y shelf contains an Ot.     -   The Ot rows represent Ot on the Y axis. This should be rare         since best practices dictate that Ot should be on the X axis.     -   XY+=Qd converts to a matrix of scatterplots. All Qds on the rows         and columns are the same.

Conversions for FIG. 4 b:

-   -   The φφ rules will drop Qd on the Y axis, unless the text or size         encoding contains a Qd. That is, if we are building a text         table, continue to build a text table; otherwise make a chart.     -   The OO rules continue to add measures to the text table.     -   The Qiφ and QiO rules create QiQd (line) graphs.     -   The φQd rules create QdQd scatterplots.     -   The OQd rules create stacked charts.     -   The QdQd rule creates a matrix of scatterplots.

Notes for FIG. 4 c:

-   -   This set of rules is used when dropping a Qd on a pane. If no         match is found, then we use the more general rules for dropping         a Qd. The goal is to try to add the Qd to the encodings when Qd         is dropped on the pane.     -   The guarded version of the *=operator only adds Qd to text or         size. If it can't, that operator is not applied.

Notes for FIG. 4 d:

-   -   Always drop Qi on the X axis.     -   But don't do it if the X axis contains a Qd.     -   If there is an existing Qi, then the Qi's are concatenated.

Notes for FIG. 4d :

-   -   Always drop Ot on the X axis.     -   If there is an existing Qi or Qd, then move the Ot leftward         until all of the Q's are to the right.

Notes for FIG. 4 g:

-   -   The += operator only adds Od to shape or color. If it can't,         that operator is not applied.     -   If no match is found, then we don't add the Od. We really want         to put Od on an encoding.

Notes for FIG. 4 i:

-   -   Do nothing if a Q is already being used.     -   Apply Qd rules if one of the O's is an Ot.     -   Adding a Qd makes a bar chart.     -   Adding an Om makes a text table.

The order in which fields are added affect the view type of the resulting view. For example, if a measure data type field is added to an empty view, and is subsequently followed by a dimension data type field, the resulting view will be a bar chart. However, if a measure data type field is added to an empty view subsequent to a dimension data type field, then the resulting view will be a text table. The resulting view's view type is thusly selected based upon a set of rules. The view type is then assigned to the resulting view and the view is then populated with data from the dataset. In one embodiment, the set of rules are predetermined. In another embodiment, the set of rules are based upon a user's preferences or actual usage. For example, a user may be given the opportunity to designate the best view type for various sequences of the addition of fields to views. Or, after the visual plot is populated and rendered for the user, the user is allowed to choose a different rendering. The user's choice as to the ultimate resulting view, if recorded, may indicate the user's preference for what view type the user considers the clear and/or useful. In yet another embodiment, heuristics may be used instead of a set of rules for selecting a resulting view.

In one embodiment, the cardinalities of the fields in the resulting view are computed and are considered in determining how the user selected fields are added. In set theory, cardinality is the size of a set. In the present invention, cardinality refers to the number of distinct instances that are associated with a field's type. For example, if a field type is “States of America”, then the cardinality of such a field would be 50.

In another embodiment, the functional dependency of the fields in the resulting view are computed and are considered in determining how the user selected fields are added. Functional dependency refers to the determination of one field by another field. For example, if one field is of the type “States of America,” and a second field is “Inches of Rainfall of the States of America,” then the second field depends upon the first. Another example is shown in FIGS. 5a -5 c. Referring to FIGS. 5a -5 c, there is a functional dependency from the Product field to the Product Type field because each product has a unique product type. This can be seen in FIG. 5a because each product (in the column where the product field resides) has a single product type (in the column where the product type field resides) to its right. When the columns are reversed in FIG. 5b , it is apparent that there is no functional dependency from the Product Type field to the Product Field because each product type has multiple products. Finally, when the fields that form a functional dependency are placed in both rows and columns (FIG. 5c ), the resulting view contains much empty space, which makes the resulting view less effective.

In yet another embodiment, in the application of the selected rule to populate the resulting view with data from the dataset, a mark is chosen for the resulting view's view type and the data from the dataset is rendered according to the mark. This is shown in FIG. 2, where, in step 218, mark chooser 126 chooses a mark for the resulting view, and data renderer 128 renders the dataset according to the mark in step 220.

FIGS. 3a and 3b show ways of operating an embodiment of the present invention. A user may drag a new field from a list of available fields and drop the field onto a view. Another way of operating an embodiment of the present invention is for the user to double click on a new field from a list of available fields. This automatically adds the new field to an existing view or automatically forms a new view if there is not an existing view. Other ways of adding or dropping fields include double clicking on a field, selecting fields, typing field names, and creating a specification for a set of fields using statistical analysis, historical analysis, or heuristic algorithms.

Now, referring to FIG. 6a a flowchart is provided for the steps through which a system proceeds in another embodiment of the present invention. First, alternative view former 130 forms alternative views of the tuples of the dataset (step 602). Resulting view selector 110 then selects a resulting view from the alternative views (step 604). Finally, dataset displayer 112 displays the dataset according to the resulting view (step 606).

In another embodiment, alternative views are formed based upon a set of criteria. FIG. 7 is a table showing the criteria for forming alternative views of a dataset and a rating system for one embodiment of the present invention. For example, if all the data in a dataset is aggregated and does not contain any independent quantitative data, then one of the possible views is a text table as determined by the first rule. Its rating is 1 meaning that it will only be the highest ranking view if other views such as Line (Measure), which was a higher rating of 9, is not applicable to the selected fields. As one skilled in the art will realize, these ratings could also be based on other criteria such as user preference, usage patterns, and statistical analysis of the data.

In one embodiment, if the user selected a first option, then the alternative views are ranked according to a rating system by alternative view ranker 134 in step 608. View assignor 120 then assigns the resulting view as the highest ranked alternative view at step 610. Dataset displayer 112 then displays the dataset according to the resulting view in step 606. For example, if all the data in a dataset is aggregated and does not contain any independently quantitative data, then alternative views of all the view types listed in FIG. 7 are generated at step 602. Then, at step 604, the text table alternative view is selected to be the resulting view, and the dataset is displayed as a text table in step 606. In another embodiment, in accomplishing step 602 (forming rated alternative views showing all tuples), view determiner 118 determines applicable view types according to the dataset's data types. Mark chooser 126 then identifies an associated mark for each applicable view type at step 620, which is then used to form alternative views for each applicable view type at step 622.

In another embodiment, if the user selected a second option, then a list of alternative views would be displayed by list displayer 136 at step 622 for the user's selection. After the user's selection is received at step 624 by selection receiver 138, the resulting view is assigned as the alternative view that the user selected by view assignor 120 at step 616, and dataset displayer 112 then displays the dataset according to the resulting view in step 606.

In yet another embodiment of the invention, cardinality computer 122 computes the cardinality of the fields in the plurality of tuples when forming the alternative views. In a further embodiment, functional dependency computer 124 computes the functional dependency of the fields in the plurality of tuples when forming the alternative views.

FIG. 8a shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a text table, or the user selected the alternative text table view. The dataset must include only aggregated data and no independently quantitative data.

FIG. 8b shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a heat map, or the user selected the alternative heat map view. The dataset must include only aggregated data, at least one field of ordinal data, one to two fields of dependent quantitative data, and no independent quantitative data.

FIG. 8c shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a side-by-side bar chart, or the user selected the alternative side-by-side bar chart view. The dataset must include only aggregated data, at least one field of ordinal data, at least one field of dependent quantitative data, and no independent quantitative data.

FIG. 8d shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a stacked bar chart, or the user selected the alternative stacked bar chart view. The dataset must include only aggregated data, at least two fields of ordinal data, at least one dependent quantitative data, and no independent quantitative data.

FIG. 8e shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a measure bar chart, or the user selected the alternative measure bar chart view. The dataset must include only aggregated data, at least one field of ordinal data, at least two fields of dependent quantitative data, and no independent quantitative data.

FIG. 8f shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a dimension line graph, or the user selected the alternative dimension line graph view. The dataset must include only aggregated data, at least one field of dependent quantitative data, at least one field of dates, and no independent quantitative data.

FIG. 8g shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a measure line graph, or the user selected the alternative measure line graph view. The dataset must include only aggregated data, at least one field of dependent quantitative data, and at least one field of independent quantitative data or dates.

FIG. 8h shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a circle graph, or the user selected the alternative circle graph view. The dataset must not include any aggregated data or independent quantitative data, and must include at least one field each of ordinal and dependent quantitative data.

FIG. 8i shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a Gantt chart, or the user selected the alternative Gantt chart view. The dataset must include only aggregated data, at least one field of ordinal data, less than three fields of dependent quantitative data, and at least one field of independently quantitative data or of relational dates.

FIG. 8j shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a single scatter plot, or the user selected the alternative single scatter plot view. The dataset must include two to four fields of dependent quantitative data, and at least one field of independent quantitative data.

FIG. 8k shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a matrix scatter plot, or the user selected the alternative matrix scatter plot view. The dataset must include three to six fields of dependent quantitative data, and at least one field of independent quantitative data.

FIG. 8l shows a rendering of the data in a dataset in an resulting view where either the highest ranked view type was a histogram, or the user selected the alternative histogram view. The dataset must include only aggregated and relational data, must have exactly one field of dependent quantitative data, and must have no independent quantitative data.

The present invention not only accepts datasets and databases as inputs, it also accepts views as inputs. A view can be used to represent a set of fields. Resulting views can also depend on the existing view. For example, rules or operators can take into account the current view to generate a new view that is related to the current view. Also, as one skilled in the art will realize, many other rules are possible, include ones to generate statistical, maps, pie charts, and three dimensional views of data.

The present invention can be implemented as a computer program product that comprises a computer program mechanism embedded in a computer readable storage medium. For instance, the computer program product could contain the program modules shown in FIG. 1. These program modules may be stored on a CD-ROM, magnetic disk storage product, or any other computer readable data or program storage product. The software modules in the computer program product can also be distributed electronically, via the Internet or otherwise, by transmission of a computer data signal (in which the software modules are embedded) on a carrier wave.

Many modifications and variations of this invention can be made without departing from its spirit and scope, as will be apparent to those skilled in the art. The specific embodiments described herein are offered by way of example only, and the invention is to be limited only by the terms of the appended claims, along with the full scope of equivalents to which such claims are entitled.

All references cited herein are incorporated herein by reference in their entirety and for all purposes to the same extent as if each individual publication or patent or patent application was specifically and individually indicated to be incorporated by reference in its entirety for all purposes. 

What is claimed is:
 1. A computer implemented method for generating a graphical representation of a dataset, comprising: at a computer having one or more processors and memory storing one or more programs configured for execution by the one or more processors: displaying a graphical user interface window including: (i) a schema display region comprising a plurality of displayed data field icons, each data field icon corresponding to a respective data field from the dataset, wherein each data field has a respective data type; (ii) a visualization region distinct from the schema display region; and (iii) a shelf region distinct from the schema display region and distinct from the visualization region, wherein the shelf region includes a plurality of shelves; detecting, via the graphical user interface window, a first user input to place a first data field icon of the plurality of data field icons from the schema display region into the visualization region, wherein the first data field icon corresponds to a first data field having a first data type; upon ceasing to detect the first user input in the visualization region: associating the first data field icon with a first shelf of the plurality of shelves according to the first data type and data types corresponding to other data field icons, if any, previously associated with shelves in the plurality of shelves; and placing the first data field icon within the first shelf; determining a view type for visualizing a portion of the dataset based, at least in part, on the first data type and the association of the first data field icon with the first shelf; and generating a graphical representation of the portion of the dataset in the visualization region in accordance with the determined view type and the data field icons associated with shelves in the plurality of shelves.
 2. The method of claim 1, wherein, prior to detecting the first user input, no data field icons are associated with the plurality of shelves.
 3. The method of claim 1, wherein: prior to detecting the first user input, at least one data field icon is associated with a second shelf of the plurality of shelves; and determining the view type is further based on the association of the at least one data field icon with the second shelf
 4. The method of claim 1, wherein: prior to detecting the first user input, at least one data field icon is associated with a second shelf of the plurality of shelves; the at least one data field icon corresponds to a second data field having a second data type; and determining the view type is further based on the second data type and the association of the at least one data field icon with the second shelf
 5. The method of claim 1, further comprising: detecting, via the graphical user interface window, a second user input to place a second data field icon of the plurality of data field icons from the schema display region into the visualization region, wherein the second data field icon corresponds to a second data field having a second data type; upon ceasing to detect the second user input in the visualization region: associating the second data field icon with a second shelf of the plurality of shelves according to the second data type and data types corresponding to other data field icons, including the first data field icon, previously associated with shelves in the plurality of shelves; and placing the second data field icon within the second shelf; determining an updated view type for visualizing an updated portion of the dataset based, at least in part, on: (i) the first data type and the association of the first data field icon with the first shelf, and (ii) the second data type and the association of the second data field icon with the second shelf; and generating an updated graphical representation of the updated portion of the dataset in the visualization region in accordance with the determined updated view type and the data field icons associated with the plurality of shelves.
 6. The method of claim 5, wherein: generating the graphical representation comprises displaying a plurality of marks in the graphical representation that correspond to the data field icons associated with shelves in the plurality of shelves, including the first data field icon; and generating the updated graphical representation comprises color encoding at least some of the plurality of marks according to data in the second data field.
 7. The method of claim 5, wherein: generating the graphical representation comprises displaying a first plurality of marks in the graphical representation that correspond to the data field icons associated with the plurality of shelves, including the first data field icon; and generating the updated graphical representation comprises displaying a second plurality of marks that correspond to the data field icons associated with the plurality of shelves, including the first data field icon and the second data field icon.
 8. The method of claim 5, wherein the view type determined based, at least in part, on the first data type and the association of the first data field icon with the first shelf is different from the view type determined based, at least in part, on (i) the first data type and the association of the first data field icon with the first shelf, and (ii) the second data type and the association of the second data field icon with the second shelf
 9. The method of claim 8, wherein the first data type is different from the second data type.
 10. The method of claim 5, wherein the view type determined based, at least in part, on the first data type and the association of the first data field icon with the first shelf is the same as the view type determined based, at least in part, on (i) the first data type and the association of the first data field icon with the first shelf, and (ii) the second data type and the association of the second data field icon with the second shelf
 11. The method of claim 10, wherein the first data type is the same as the second data type.
 12. The method of claim 1, wherein generating the graphical representation comprises displaying a plurality of marks in the graphical representation that correspond to the data field icons associated with the plurality of shelves, including the first data field icon.
 13. The method of claim 1, wherein: prior to detecting the first user input, at least two data field icons are associated with two shelves of the plurality of shelves; the first shelf is a color encoding shelf distinct from the two shelves of the plurality of shelves; and generating the graphical representation comprises color encoding a plurality of marks that correspond to the at least two data field icons according to data in the first data field.
 14. The method of claim 1, wherein the respective data type of each data field is selected from the group consisting of ordinal, independent quantitative, and dependent quantitative.
 15. The method of claim 1, wherein the respective data type of each data field is selected from the group consisting of ordinal, ordinal time, dependent ordinal, quantitative, independent quantitative, dependent quantitative, quantitative time, and quantitative position.
 16. A computer system for generating graphical representations, comprising: one or more processors; memory; and one or more programs stored in the memory and configured for execution by the one or more processors, the one or more programs comprising instructions for: displaying a graphical user interface window including: (i) a schema display region comprising a plurality of displayed data field icons, each data field icon corresponding to a respective data field from the dataset, wherein each data field has a respective data type; (ii) a visualization region distinct from the schema display region; and (iii) a shelf region distinct from the schema display region and distinct from the visualization region, wherein the shelf region includes a plurality of shelves; detecting, via the graphical user interface window, a first user input to place a first data field icon of the plurality of data field icons from the schema display region into the visualization region, wherein the first data field icon corresponds to a first data field having a first data type; upon ceasing to detect the first user input in the visualization region: associating the first data field icon with a first shelf of the plurality of shelves according to the first data type and data types corresponding to other data field icons, if any, previously associated with shelves in the plurality of shelves; and placing the first data field icon within the first shelf; determining a view type for visualizing a portion of the dataset based, at least in part, on the first data type and the association of the first data field icon with the first shelf; and generating a graphical representation of the portion of the dataset in the visualization region in accordance with the determined view type and the data field icons associated with shelves in the plurality of shelves.
 17. The computer system of claim 16, wherein, prior to detecting the first user input, no data field icons are associated with the plurality of shelves.
 18. The computer system of claim 16, wherein: prior to detecting the first user input, at least one data field icon is associated with a second shelf of the plurality of shelves; and determining the view type is further based on the association of the at least one data field icon with the second shelf
 19. The computer system of claim 16, wherein: prior to detecting the first user input, at least one data field icon is associated with a second shelf of the plurality of shelves; the at least one data field icon corresponds to a second data field having a second data type; and determining the view type is further based on the second data type and the association of the at least one data field icon with the second shelf
 20. A non-transitory computer-readable storage medium storing one or more programs configured for execution by a computer system having one or more processors, and memory, the one or more programs comprising instructions for: displaying a graphical user interface window including: (i) a schema display region comprising a plurality of displayed data field icons, each data field icon corresponding to a respective data field from the dataset, wherein each data field has a respective data type; (ii) a visualization region distinct from the schema display region; and (iii) a shelf region distinct from the schema display region and distinct from the visualization region, wherein the shelf region includes a plurality of shelves; detecting, via the graphical user interface window, a first user input to place a first data field icon of the plurality of data field icons from the schema display region into the visualization region, wherein the first data field icon corresponds to a first data field having a first data type; upon ceasing to detect the first user input in the visualization region: associating the first data field icon with a first shelf of the plurality of shelves according to the first data type and data types corresponding to other data field icons, if any, previously associated with shelves in the plurality of shelves; and placing the first data field icon within the first shelf; determining a view type for visualizing a portion of the dataset based, at least in part, on the first data type and the association of the first data field icon with the first shelf; and generating a graphical representation of the portion of the dataset in the visualization region in accordance with the determined view type and the data field icons associated with shelves in the plurality of shelves. 